added preserve validation function #182
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Feature enhancement
Issue Number:
Screenshots/videos:
tour.mp4
If relevant, did you update the documentation?
No documentation updates required for this feature.
Summary
This pull request addresses a critical UX issue by implementing persistent client-side storage of validation results and user code using localStorage with namespaced keys (
validation-{chapterIndex}-{stepIndex}). The solution enhances state management through Zustand integration, enabling seamless data restoration and mutation across component lifecycles.Technical Implementation:
useValidationRestore) orchestrating state restoration via useEffect with SSR compatibility checksDoes this PR introduce a breaking change?
No